- created example for ModelVariables in modelDescription.xml #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an example how I interpret the required configuration if an internal XCP slave. The XML schema requires a different kind of start value configuration for simple types (Boolean, UInt16) and strings. According to https://github.com/modelica/fmi-standard/blob/main/schema/fmi3Variable.xsd#L331 it is not enforced that exact one start value is given (minOccurs="0" maxOccurs="unbounded"). This should be described in the layered standard as an obligation of the importer.
I will take this a todo for me in addition to referring to the example in the document.